Summary

• Add legal_status column to screened_patents table to separately track patent legal status from relevance judgment
• Fix abstract_text source: screening skill now explicitly requires fetch_patent.abstract_text instead of search snippet
• Batch parallel fetch: screening now fetches up to 10 patents in parallel instead of sequential one-by-one

Problem

The screening skill was storing search result snippets as abstract_text instead of the official patent abstract from fetch_patent. Additionally, judgment conflated two separate concerns (relevance assessment and legal status) into a single field with no column to store legal_status from fetch_patent.

Root causes:

1. screened_patents table had no legal_status column — fetched legal status was discarded
2. SKILL.md did not explicitly distinguish abstract_text from snippet
3. Tests only verified fetch_patent was invoked, not that results were correctly used
4. Sequential per-patent processing was unnecessarily slow

Test plan

• screening/functional-with-data PASS — verifies fetch_patent invoked, legal_status recorded, all patents screened
• screening/triggering PASS
• evaluating/functional PASS — verifies fetch_patent invoked
• evaluating/triggering PASS
• Remaining tests (claim-analyzing, prior-art-researching, investigation-reporting) — schema change propagated to all test fixtures

🤖 Generated with Claude Code